-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uniformize kwargs for Paligemma processor and update docs #33571
Uniformize kwargs for Paligemma processor and update docs #33571
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beautiful! Thanks a lot :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding!
Main comment is just about the default for tokenize_newline_separately
if sys.version_info >= (3, 11): | ||
from typing import Unpack | ||
else: | ||
from typing_extensions import Unpack |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes! I'll open a PR to do a batch replace towards
from processing_utils import Unpack
5ccdb6e
to
8e6b55b
Compare
…e#33571) * Uniformize paligemma processor * nit
…e#33571) * Uniformize paligemma processor * nit
Hey. Thanks for taking this up and continuing on my PR and completing it. I was caught up with a lot of work and wasn't able to fix issues after the last iteration. |
What does this PR do?
Adds uniformized processors kwargs following #31911 for Paligemma.
Continuation of #32377 .
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@molbap @amyeroberts